Action items
Collimator
Google drive ownership issue. When created a copy of a file, the original owner is shown as the owner of the copy as well. Ask google help on what is the implication of that?
Pavan: Tried to reproduce this. The claim is no longer true. When a copy is created, it's ownership is with the new GDrive account.
Move collimator projects to
hydrotrek@gqc.comcollimator as the owner.- Added
hydrotrek@gqc.comas an admin of the project.
- Added
Review all documents of
Collimatorand have them in the people.gqc.com- Discussed with Vannary and filed a github issue for Sudhir's review.
CCTV
- Test stitching full frames together and compare the results
- Document nbdev to github integration and colab to github integration (There is a merge conflict)
- Colab to git integration is documented.
- git_nb
- git pull requiring credentials everytime
- Colab to git integration is documented.
- Make the enhancement changes to the
cctv-appspages and handover to Srujana to test.- Video-player app
- Distance region extraction app
- SD1 dataset next steps
IoT
Test the grafana cutomer support workaround on exporting and importing grafana alerts between instances. (They mentioned that it should work on grafana cloud as well)
Using the EZsbc battery monitor code from github
IIS3DWB sensor kit prototype development
- Collecting information on the external components used.
Document the code using Doxygen
a Azure linux function app to do CEEMDAN from the TDEngine cloud data
Test USB connection in
USB-to-Socketrepo with two S3 nodes.- Not working right-off-the bat. Need to cross check with the USB-host on DeepVibe server and the changes in the flow between USB device example and the root node USB device implementation.
- Test curl function in root node.
- Attempting this with HTTP client API in ESP32
Check making the deep_vibe server multi threaded. -- low priority
Test out Elsevier API for AI3
- colab notebook
- Should we create a UI for easy access?
DeepVibe Server
- Find more on the logging function used in
systemctl.- Modifying logging level, etc. https://www.loggly.com/ultimate-guide/linux-logging-with-systemd/
- Clear the log at each restart of the service
- Rewrite the readme of the deep_vibe_app repo.
- Find where to place the exe file for a service (compared to referring to the exe in the repo folder)
> `/usr/local/bin/` is a standard location according to [this](https://www.baeldung.com/linux/bin-sh-installers#:~:text=2.%20Binary%20Files,local/bin).
Moved the `deep_vibe` binary to /usr/local/bin

- Find more on the logging function used in
AgPoint
- Documenting the code to identify the underlying algorithm
- Identify stepper moter config to use
- Test the proposed new logic to account for the offset
AI3
- Find if they have made any changes to the rules. Specifically check if we are allowed to bring a laptop in.